| Field
|
Setting
|
|---|
| Group Type
|
h.323
|
| Remote Office?
|
n
|
| Max number of NCA TSC
|
10
|
| Max number of CA TSC
|
10
|
| Trunk Group for NCA TSC
|
(Leave blank)
|
| Trunk Group for Channel Selection
|
(Leave blank)
|
| TSC Supplementary Service Protocol
|
b
|
| Near-end Node Name
|
procr (IPv4 IP address) or procr6 (IPv6 IP address) name of the CLAN, depending on which interface connects to Communication Manager Messaging.
|
| Far-end Node Name
|
Name of the messaging server, in IPv4 or IPv6 IP address format, that is resident on the Communication Manager Messaging server. This name is the same name that appears on the Node Names screen and has the Integrated Messaging IP address.
|
| Near-end Listen Port
|
1720
|
| Far-end Listen Port
|
11720
|
| Far-end Network Region
|
1 is usually assigned to procr. If this field is left blank, Communication Manager uses the network region associated with the near-end node name.
|
| Calls Share IP Signaling Connection?
|
y
|
| DTMF over IP
|
out-of-band
|
| Enable Layer 3 Test?
|
y
|
| Direct IP-IP Audio Connections?
|
y
|
| IP Audio Hairpinning?
|
n
|
| Interworking Message
|
PROGress
|
Note The fields that must be left blank must not have any values entered at this time. The values are populated later in the administration process.
The field, Far-end Network Region, defaults to 1 if a value is not specified.
The Calls Share IP Signaling Connection field is set to y so that messaging does not attempt to create a new TCP/IP connection for each call.
Note If the configuration of the Far-end Network Region field changes, the signaling group may not function correctly for messaging.
The Far-end Listen port and Near-end Listen Port have the values 11720 and 1720 respectively. This is because Communication Manager and Communication Manager Messaging share the same IP address.